Repository navigation
feat(registry): viva-pde-particle composed, for the PDE + particle + ODE mash-up (composition 7c-4) - #450
Merged
Conversation
…ODE mash-up (composition 7c-4) - Entries: smoldyn-vcell (the OPTION_VCELL wheel from virtualcell/Smoldyn's release vcell-pyhybrid-e86d552, by URL and sha256), vcell-fenics (git), pyvcell-fvsolver 0.11.1, zarr 3.4.1. viva-pde-particle gains its install (git 8c16827, the deployed image's commit; the `reference` extra), its conda engines and `requires`. - A prebuilt image's members include its bundled entries' requirements, which it installs its own way: a document of viva-pde-particle's classes alone still runs in its image (D7c.3) instead of making a mash-up. - Compliance case viva-pde-particle/fokker-planck-ensemble: its own seeded four-trial PDE + Smoldyn ensemble, emitter fully qualified (D7c.2). A scalar expectation's field may be a path (values.2.0). - Not offered anywhere, such a document now needs a mash-up, so an anonymous caller is told to sign in (401) instead of refused as not installed. Checked with compose-api's code in Docker: EnsembleRunner + CopasiUTCStep + RAMEmitter resolves to mash-05956395cf, locks (462 packages), passes the URL check, installs, and both cases pass compose-api's evaluator. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
viva-pde-particle#67 replaced EnsembleRunner, which imported whatever "module:function" a document's config named, with one Ensemble class per trial function. The entry installs its merge commit, the compliance case names FokkerPlanckEnsemble with no trial in its config (the values are unchanged), and the plan records the decision and that the prebuilt image moves to the same commit as viva-pde-particle@2. Checked in Docker with compose-api's own code: the mash-up with COPASI locks, passes its URL check, installs, and both compliance cases pass. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part 7c-4 of
docs/plan-environment-composition.md. It is the last piece before 7c-5, the live run.Changes
kind: library):smoldyn-vcell: theOPTION_VCELLwheel from virtualcell/Smoldyn's releasevcell-pyhybrid-e86d552, built by its workflow (ci: build the OPTION_VCELL Python wheel for compose-api, and release it virtualcell/Smoldyn#1, 7c-3). It installs by URL and sha256bb033bcc…, which I checked on download.vcell-fenics(git4dab281),pyvcell-fvsolver0.11.1,zarr3.4.1.install: git21dfe46, fix(ensemble): one Process class per trial function, nothing imported from config vivarium-collective/viva-pde-particle#67's merge, with thereferenceextra;requiresfor the libraries above, plus pyvcell and libvcell.members_offor a prebuilt image now includes its bundled entries' requirements, which the image installs its own way. Without this, a document of viva-pde-particle's classes alone would no longer be covered by its image and would make a mash-up. The tests caught it.viva-pde-particle/fokker-planck-ensemble: its own example, four seeded PDE + Smoldyn trials, with the emitter fully qualified (D7c.2), and the seeded results as exact expectations. To support it, ascalarexpectation'sfieldmay now be a path (values.2.0).Checked with compose-api's own code, in Docker (linux/amd64, the pinned pixi image), for a document of
FokkerPlanckEnsemble+CopasiUTCStep+RAMEmitter(rerun at21dfe46):needed_entriesgives ten entries; no declared environment covers them;composableagrees, so the service would makemash-05956395cf.pixi.tomllocked in 45 s (462 packages)._url_checks, from 7c-2) passed against the release.pixi install --frozensucceeded.find_violationsadmits the case document in the mash-up.Tests: the case and the
scalarpath, the mash-up admitting all three classes, and the prebuilt image still chosen for viva-pde-particle's classes alone.make checkpasses. The full suite has only the 3 known order-dependent local failures.EnsembleRunner(decided): it imported whatever itstrial: "module:function"config named. viva-pde-particle#67 replaced it with oneEnsembleclass per trial function, so the case document nameslocal:viva_pde_particle.ensemble.FokkerPlanckEnsembleand its config has notrial. The expected values are unchanged. The prebuilt image moves to the same commit as viva-pde-particle@2, an admin registration rather than a code change.🤖 Generated with Claude Code